bq27441: Fix checksum overflow in compute_block_checksum().#161
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Fixes a bug in compute_block_checksum() where the sum of 32 data bytes could exceed 255, causing a negative checksum value and a ValueError when writing to the register. The fix masks the sum to a single byte before computing the complement.
Changes:
- Mask the intermediate checksum sum to 8 bits before subtracting from 255, preventing negative/out-of-range values.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
🎉 This PR is included in version 0.0.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #162
Summary
Fix a pre-existing bug where
compute_block_checksum()could produce a negative value when the sum of the 32 data bytes exceeds 255. This causedValueError: bytes value out of rangein_write_reg()during__init__→power_on()→set_capacity()→write_extended_data().Root cause
Fix
This bug has existed since the initial driver commit but only manifests on real hardware (mock I2C returns zeroed data that stays within range).
Test plan
Mock tests
Hardware tests